Domain INFO Request
Function
This request is used to query the data of a domain.
Requirements
The domain must exist.
Features
The data output varies, depending on whether the field "recursive" has the value "true" or "false", see Documentation DENIC-31.
With an Authinfo1 or Authinfo2, the owner data (Holder) of own and foreign domains can be queried as often as required until the expire date or until used in a CHPROV or CHHOLDER request.
| K/V Keyword | XML Namespace and Element | Occurrence min - max |
Type / Length | Value Range | Description |
|---|---|---|---|---|---|
| Action | domain:info | 1 | enumeration | info-erule | This is the request type. |
| Version | - | 1 | enumeration | version-erule | This is the version. The keyword is only relevant for requests in the key/value format. |
| Domain | domain:handle | 1 | token 4 - 66 |
domain-rule | This is the name of the domain. |
| Domain-Ace | domain:ace | 0 - 1 | token 4 - 66 |
domainace-rule | This is the ACE form (ASCII Compatible Encoding) of the domain name. |
| AuthInfo | domain:authInfo | 0 -1 | enumeration | - | AuthInfo1 or AuthInfo2 |
| Recursive | "recursive" attribute for the "domain:info" element | 0 - 1 | boolean | boolean-erule | If "recursive = true" is set, the Contact data will be included in the output. |
Common Mistakes
The domain stated in the request does not exist.
Examples
For a domain INFO response, the data is grouped into multiple records in either CSV or XML format.
In the domain INFO response, the number of records and their level of detail can vary. This depends on the query parameters and whether the RegAcc used to query the domain information has the required authorization.
Explanation of the examples in the tables
IThe table explains the data records from the left column of the comparison table with the examples (at the end of the topic, can be expanded).
| Record | Line Numbers | Explanation |
|---|---|---|
| Status query | 1 - 2 | Confirmation of whether the query was successful or failed |
| Domain data | 4 - 11 |
|
| General Request (optional) | 13 - 17 |
|
| Abuse Contact (optional) | 19 - 23 | The meaning of the information in the data set for “Abuse Contact” is the same as for the data set “General Request”. |
| Domain holder | 25 - 35 |
|
| Verification informations (optional) | 37 - 44 | For details, see Verification - Formats, Types, Values |
| Further domain holders and verification informations (optional) | 46 - 75 | - |
|
Registration account |
|
Registrar information:
|
Special feature of the domain owner and the verification information in K/V format
-
In the K/V request, the domain holder and verification data records that belong together are listed one below the other.
-
The date ("changed”) is displayed for domain holders, but it also applies to the associated verification data.
Special feature of the registration date
-
In isolated cases, no registration date may be available. Instead, the earliest internal system process date that can be determined for a domain is displayed. Domains without a registration date are displayed with the prefix “before”:
CopyRegistrationDate: before 2011-05-31T00:00:00+02:00
Special feature of the "changed" date
In the case of a foreign domain, changed data may not be visible because the information is restricted due to the parameters of the request.
This is the case in the verification information, for example, if the value for “VerificationReference” has been changed.
In the result of the request, the domain owner record (type ORG) displays the changed date, but "VerificationReference" is not visible in the associated verification information.
Special note on deadlines
If a risk assessment has been carried out for a domain and the result is that the contact(s) must be verified, the deadline lines will show date and time information indicating a deadline. Verification must be carried out by these deadlines, otherwise certain actions will be taken when the dates expire:
-
VerificationDeadlineBeforeDedelegation: When the deadline expires, the name servers for the domain will be removed from the.de zone.
-
VerificationDeadlineBeforeDeletion: Once the deadline has passed, the domain is deleted (DELETE) by DENIC, without RGP.
Deadlines are not issued with an invalid AuthInfo password.
Example
VerificationDeadlineBeforeDedelegation: 2024-06-05T00:00:00+02:00
VerificationDeadlineBeforeDeletion: 2024-09-05T00:00:00+02:00The format of the time specification is explained under Verification - Formats, Types, Values.
Special feature of the RegAcc data set
More detailed information about the registration account and the member can be requested with the RegAcc INFO request. A domain INFO request displays the compact information shown in the examples.
Special feature of keywords
In compound words, the Camelcase spelling is used, in which the first letter of a word is capitalized.
Special features of the domain status
The possible statuses are displayed under Domain INFO: “connect”, “failed”, “pendingCreate” and “serverHold”. For more information on “pendingCreate” and “serverHold”, see Domain CREATE Request.
| Caution! | When making a request using RRI protocol version 4.0, the status “failed” is issued for domains that are in the “pendingCreate” or “serverHolder” status. |
Response Examples
The table compares the results of Domain INFO responses queried with different administrative statuses and parameters.
| Your Domain, recursive | Your Domain, no recursive | Domain of other Holder, recursive, with AuthInfo | Domain of other Holder, recursive, without AuthInfo | Domain of other Holder, no recursive, without AuthInfo |
|---|---|---|---|---|
|
Copy
Response Domain INFO - your domain, recursive |
Copy
Response K/V Domain INFO - your domain, not recursive |
Copy
Response Domain INFO - ohter domain, recursive, with AuthInfo |
Copy
Response Domain INFO - ohter domain, recursive, with AuthInfo |
Copy
Response Domain INFO - ohter domain, recursive, with AuthInfo |